Augmented reality system

ABSTRACT

An augmented reality system to generate and cause display of a presentation of a space at a first client device, receive one or more selections of points within the presentation of the space at the first client device, and render graphical elements at the one or more points within the presentation of the space at the first client device. The augmented reality system is further configured to receive a display request to display the space at a second client device, and in response, may render a second presentation of the space at the second client device, wherein the second presentation of the space includes the graphical elements at the one or more points.

CLAIM OF PRIORITY

This application is a continuation of U.S. patent application Ser. No.15/706,074, filed on Sep. 15, 2017, which is incorporated herein byreference in its entirety.

TECHNICAL FIELD

Embodiments of the present disclosure relate generally to mobilecomputing technology and, more particularly, but not by way oflimitation, to systems for generating and presenting augmented realitymedia content.

BACKGROUND

Augmented reality (AR), is a live direct or indirect view of a physical,real-world environment whose elements are augmented bycomputer-generated sensory inputs.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 is a block diagram showing an example messaging system forexchanging data (e.g., messages and associated content) over a networkin accordance with some embodiments, wherein the messaging systemincludes an engagement tracking system.

FIG. 2 is block diagram illustrating further details regarding amessaging system, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored inthe database of the messaging server system, according to certainexample embodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 5 is a schematic diagram illustrating an example access-limitingprocess, in terms of which access to content (e.g., an ephemeralmessage, and associated multimedia payload of data) or a contentcollection (e.g., an ephemeral message story) may be time-limited (e.g.,made ephemeral) in accordance with some embodiments.

FIG. 6 is a block diagram illustrating various modules of an augmentedreality system, according to certain example embodiments.

FIGS. 7A/B include depictions of exemplary graphical user interfaces todisplay augmented reality presentations of media content, according tocertain example embodiments.

FIG. 8 is a flowchart illustrating a method for causing display of anaugmented reality presentation of a space, according to certain exampleembodiments.

FIG. 9 is a flowchart illustrating a method for causing display of anaugmented reality presentation of a space, according to certain exampleembodiments.

FIG. 10 is a flowchart illustrating a method for causing display of anaugmented reality presentation of a space, according to certain exampleembodiments.

FIG. 11 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described and used to implement variousembodiments.

FIG. 12 is a block diagram illustrating components of a machine,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

Embodiments of the present disclosure relate generally to mobilecomputing technology and, more particularly, but not by way oflimitation, to systems for generating and presenting augmented realitymedia content. An Augmented Reality (AR) system as described herein maybe or include any instrumentality or aggregate of instrumentalitiesoperable to compute, process, store, display, generate, communicate, orapply various forms of data for generating and presenting interfaces forthe display of AR media content.

In accordance with various embodiments described herein, an AR systemgenerates and causes display of a presentation of a space at a firstclient device, receives one or more selections of points within thepresentation of the space at the first client device, and rendersgraphical elements at the one or more points within the presentation ofthe space at the first client device. The AR system is furtherconfigured to receive a display request to display the space at a secondclient device, and in response, may render a second presentation of thespace at the second client device, wherein the second presentation ofthe space includes the graphical elements at the one or more points.

In some example embodiments, the AR system retrieves location data thatidentifies a location of the first client device in response toreceiving the selections of the one or more points within thepresentation of the space. Based on the location data, the AR systemdetermines a perspective of the first client device relative to the oneor more points. The perspective of the first client device indicates a“point of view” of the device when viewing the one or more points. TheAR system determines an orientation of each of the graphical elementsbased on the perspective of the first client device relative to the oneor more points. The AR system renders the graphical elements based onthe determined orientations, at the one or more points within thepresentation of the space.

Similarly, in some embodiments the AR system retrieves location datacorresponding to the second client device in response to receiving arequest to display a presentation of the space that includes the one ormore points selected at the first client device. The AR systemdetermines a perspective of the second client device based on thelocation data of the second client device relative to the one or morepoints, and determines orientations of the graphical elements based onthe perspective of the second client device. The AR system renders thegraphical elements within the presentation of the space at the secondclient device based on the determined orientations, at the one or morepoints within the space. In this way, the graphical elements may berendered and re-rendered based on a location of a client device.

In some example embodiments, the graphical element may be displayedwithin the presentation of the space with an indication of a location ofa client device. For example, in response to receiving a selection of apoint within a presentation of a space from a first client device, theAR system may retrieve location data that identifies the location of thefirst client device, and renders the graphical element at the pointwithin the presentation of the space, along with an indication of thelocation of the first client device. The indication of the location ofthe first client device may include an arrow, or similar visualindicator. In some embodiments, the graphical element may appear as aprojection emanating from a source at the location of the first clientdevice, with a visible projection beam extending from the location ofthe first client device and terminating at the point with the graphicalelement.

In some example embodiments, the indication of the location of theclient device may be personalized based on user inputs. For example, auser of the first client device may additionally provide a selection ofproperties of the indication of the location. The properties may forexample include size, color, style, animation, etc. In response, the ARsystem renders the graphical element at the selected point with theindication of the location based on the properties selected by the user.

Consider an illustrative example from a user perspective, demonstratingembodiments wherein two users at two distinct client devices maycommunicate with one another through the use of media content displayedin an AR interface. A first user of a first client device may display apresentation of a space at the first client device—for example, thespace may be a view point of a landscape. The first user may be at asouthern most point in a city, viewing a skyline of the city from afirst perspective. The first user may provide an input into thepresentation of the space, to select a specific point above the skyline.In response to receiving the selection of the point within thepresentation of the space, the AR system retrieves location datacorresponding to the first client device, and causes display of a set ofgraphical elements at the first client device. The set of graphicalelements may include graphical representations of objects with animationsuch as balloons, fireworks, hot air balloons, blimps etc., or may alsoinclude an option to enable to the user to select a graphical elementfrom an external source. In some embodiments, the AR system may alsoprovide an interface to receive a text string, wherein the graphicalelement selected by the user may be modified to include the text string.

The first user may thereby provide an input selecting a graphicalelement from among the set of graphical elements, or may provide aninput drawing a graphical element directly onto the presentation of thespace. In some embodiments, the user may both select a graphical elementand draw a graphical element, wherein both graphical elements may bedisplayed together. For example, a user may select a graphical elementand provide further inputs drawing or making changes to the graphicalelement, such as changing a color of the graphical element, adding linesor details to the graphical element, or editing text associated with thegraphical element. For purposes of this illustrative example, the firstuser may provide an input selecting a graphical icon representative of ablimp. In response to receiving the selection of the graphical element,the AR system determines a perspective of the first client device basedon the location data and the point selected by the first user. Based onthe perspective, the AR system determines an orientation to display thegraphical element of the blimp within the presentation of the space. Insome embodiments, the first user may additionally provide directionalinputs to set the full position and orientation of the graphical elementwithin the presentation of the space. For example, the user may provideinputs to rotate, and translate the graphical element within thepresentation of the space.

The AR system causes display of the graphical element within thepresentation of the space at the first client device. From theperspective of the first user, the presentation of the space (whichincludes a skyline of the city) includes a blimp at the locationselected by the user. As the user traverses and changes location, the ARsystem may make adjustments to the orientation of the blimp inreal-time, giving the illusion that the blimp is floating above theskyline, at the location which the user selected.

The AR system next receives a request to display a presentation of thespace (e.g., the skyline) from a second client device. In response toreceiving the request to display the presentation of the space, the ARsystem retrieves location data corresponding to the second clientdevice. Based on the location data of the second client device, the ARsystem determines an appropriate orientation of the blimp (the graphicalelement) at the point within the presentation of the space at the secondclient device. The AR system then generates and displays thepresentation of the space at the second client device, with the blimp atthe appropriate orientation.

The user of the second client device may provide inputs into thepresentation of the space, to interact with the graphical element. Inresponse to receiving the inputs interacting with the graphical elementfrom the second client device, the AR system alters the graphicalelement in the presentation at both the first client device and thesecond client device. For example, the second user may provide an inputto “pop” the blimp. In response to receiving the input, the AR systemalters the presentation to depict a change in the graphical element—forexample, the blimp may deflate or fall from the point in the skyline.

Accordingly, each messaging client application 104 is able tocommunicate and exchange data with another messaging client application104 and with the messaging server system 108 via the network 106. Thedata exchanged between messaging client applications 104, and between amessaging client application 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality either within the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Insome embodiments, this data includes, message content, client deviceinformation, geolocation information, media annotation and overlays,message content persistence conditions, social network information, andlive event information, as examples. In other embodiments, other data isused. Data exchanges within the messaging system 100 are invoked andcontrolled through functions available via user interfaces (UIs) of themessaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server110, this server receives and transmits message data (e.g., commands andmessage payloads) between the client device 102 and the applicationserver 112. Specifically, the Application Program Interface (API) server110 provides a set of interfaces (e.g., routines and protocols) that canbe called or queried by the messaging client application 104 in order toinvoke functionality of the application server 112. The ApplicationProgram Interface (API) server 110 exposes various functions supportedby the application server 112, including account registration, loginfunctionality, the sending of messages, via the application server 112,from a particular messaging client application 104 to another messagingclient application 104, the sending of media files (e.g., images orvideo) from a messaging client application 104 to the messaging serverapplication 114, and for possible access by another messaging clientapplication 104, the setting of a collection of media data (e.g.,story), the retrieval of a list of friends of a user of a client device102, the retrieval of such collections, the retrieval of messages andcontent, the adding and deletion of friends to a social graph, thelocation of friends within a social graph, opening and application event(e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116, a social network system 122, and an AR system124. The messaging server application 114 implements a number of messageprocessing technologies and functions, particularly related to theaggregation and other processing of content (e.g., textual andmultimedia content) included in messages received from multipleinstances of the messaging client application 104. As will be describedin further detail, the text and media content from multiple sources maybe aggregated into collections of content (e.g., called stories orgalleries). These collections are then made available, by the messagingserver application 114, to the messaging client application 104. Otherprocessor and memory intensive processing of data may also be performedserver-side by the messaging server application 114, in view of thehardware requirements for such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions services, and makes these functions and services available tothe messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph 304 within thedatabase 120. Examples of functions and services supported by the socialnetwork system 122 include the identification of other users of themessaging system 100 with which a particular user has relationships oris “following,” and also the identification of other entities andinterests of a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message,collection of messages (e.g., a SNAPCHAT story), or graphical element,selectively display and enable access to messages and associated contentvia the messaging client application 104. Further details regarding theoperation of the ephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image video and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text and audio) may be organized into an “eventgallery” or an “event story.” Such a collection may be made availablefor a specified time period, such as the duration of an event to whichthe content relates. For example, content relating to a music concertmay be made available as a “story” for the duration of that musicconcert. The collection management system 204 may also be responsiblefor publishing an icon that provides notification of the existence of aparticular collection to the user interface of the messaging clientapplication 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion of usergenerated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay (e.g., a SNAPCHAT filter) to themessaging client application 104 based on a geolocation of the clientdevice 102. In another example, the annotation system 206 operativelysupplies a media overlay to the messaging client application 104 basedon other information, such as, social network information of the user ofthe client device 102. A media overlay may include audio and visualcontent and visual effects. Examples of audio and visual content includepictures, texts, logos, animations, and sound effects. An example of avisual effect includes color overlaying. The audio and visual content orthe visual effects can be applied to a media content item (e.g., aphoto) at the client device 102. For example, the media overlayincluding text that can be overlaid on top of a photograph generatedtaken by the client device 102. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice beach), aname of a live event, or a name of a merchant overlay (e.g., BeachCoffee House). In another example, the annotation system 206 uses thegeolocation of the client device 102 to identify a media overlay thatincludes the name of a merchant at the geolocation of the client device102. The media overlay may include other indicia associated with themerchant. The media overlays may be stored in the database 120 andaccessed through the database server 118.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map, and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay should be offered to other users. Theannotation system 206 generates a media overlay that includes theuploaded content and associates the uploaded content with the selectedgeolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest bidding merchant with a corresponding geolocationfor a predefined amount of time

FIG. 3 is a schematic diagram 300 illustrating data 300 which may bestored in the database 120 of the messaging server system 108, accordingto certain example embodiments. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table314. The entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events etc. Regardless of type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters, in an annotation table 312. Filters for which data is storedwithin the annotation table 312 are associated with and applied tovideos (for which data is stored in a video table 310) and/or images(for which data is stored in an image table 308). Filters, in oneexample, are overlays that are displayed as overlaid on an image orvideo during presentation to a recipient user. Filters may be of variestypes, including a user-selected filters from a gallery of filterspresented to a sending user by the messaging client application 104 whenthe sending user is composing a message. Other types of filers includegeolocation filters (also known as geo-filters) which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client application 104, basedon geolocation information determined by a GPS unit of the client device102. Another type of filer is a data filer, which may be selectivelypresented to a sending user by the messaging client application 104,based on other inputs or information gathered by the client device 102during the message creation process. Example of data filters includecurrent temperature at a specific location, a current speed at which asending user is traveling, battery life for a client device 102 or thecurrent time.

Other annotation data that may be stored within the image table 308 isso-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video or audio data, which are compiled into acollection (e.g., a SNAPCHAT story or a gallery). The creation of aparticular collection may be initiated by a particular user (e.g., eachuser for which a record is maintained in the entity table 302) A usermay create a “personal story” in the form of a collection of contentthat has been created and sent/broadcast by that user. To this end, theuser interface of the messaging client application 104 may include anicon that is user selectable to enable a sending user to add specificcontent to his or her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automaticallyor using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users, whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story”,which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some in some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102, and that is included in the message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from the memory component of the client        device 102, and that is included in the message 400.    -   A message annotations 412: annotation data (e.g., filters,        stickers or other enhancements) that represents annotations to        be applied to message image payload 406, message video payload        408, or message audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address or device identifier)        indicative of a user of the client device 102 on which the        message 400 was generated and from which the message 400 was        sent    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address or device identifier)        indicative of a user of the client device 102 to which the        message 400 is addressed.

The contents (e.g. values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message story 504) may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, where the messaging client application 104 is a SNAPCHATapplication client, an ephemeral message 502 is viewable by a receivinguser for up to a maximum of 10 seconds, depending on the amount of timethat the sending user specifies using the message duration parameter506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message story 504 (e.g., a personal SNAPCHAT story, or anevent story). The ephemeral message story 504 has an associated storyduration parameter 508, a value of which determines a time-duration forwhich the ephemeral message story 504 is presented and accessible tousers of the messaging system 100. The story duration parameter 508, forexample, may be the duration of a music concert, where the ephemeralmessage story 504 is a collection of content pertaining to that concert.Alternatively, a user (either the owning user or a curator user) mayspecify the value for the story duration parameter 508 when performingthe setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral messagestory 504 has an associated story participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message story504. Accordingly, a particular ephemeral message story 504 may “expire”and become inaccessible within the context of the ephemeral messagestory 504, prior to the ephemeral message story 504 itself expiring interms of the story duration parameter 508. The story duration parameter508, story participation parameter 510, and message receiver identifier424 each provide input to a story timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message story 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message story 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the story timer 514 operationally controls the overalllifespan of an associated ephemeral message story 504, as well as anindividual ephemeral message 502 included in the ephemeral message story504. In one embodiment, each and every ephemeral message 502 within theephemeral message story 504 remains viewable and accessible for atime-period specified by the story duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message story 504, based on a story participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message story 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message story 504based on a determination that it has exceeded an associated storyparticipation parameter 510. For example, when a sending user hasestablished a story participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message story 504 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message story 504 either when the storyparticipation parameter 510 for each and every ephemeral message 502within the ephemeral message story 504 has expired, or when theephemeral message story 504 itself has expired in terms of the storyduration parameter 508.

In certain use cases, a creator of a particular ephemeral message story504 may specify an indefinite story duration parameter 508. In thiscase, the expiration of the story participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message story504 will determine when the ephemeral message story 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage story 504, with a new story participation parameter 510,effectively extends the life of an ephemeral message story 504 to equalthe value of the story participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message story 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client application 104to cause an indicium (e.g., an icon) associated with the relevantephemeral message story 504 to no longer be displayed within a userinterface of the messaging client application 104. Similarly, when theephemeral timer system 202 determines that the message durationparameter 506 for a particular ephemeral message 502 has expired, theephemeral timer system 202 causes the messaging client application 104to no longer display an indicium (e.g., an icon or textualidentification) associated with the ephemeral message 502.

FIG. 6 is a block diagram illustrating components of the AR system 124,that configure the AR system 124 to cause display of a presentation of aspace at a client device, receive a selection of a point within thepresentation of the space from the client device, and render a graphicalelement at the point within the space, according to some exampleembodiments. The AR system 124 is shown as including a display module602, an augmented reality module 604, a personalization module 606, anda location module 608, all configured to communicate with each other(e.g., via a bus, shared memory, or a switch). Any one or more of thesemodules may be implemented using one or more processors 610 (e.g., byconfiguring such one or more processors to perform functions describedfor that module) and hence may include one or more of the processors610.

Any one or more of the modules described may be implemented usinghardware alone (e.g., one or more of the processors 610 of a machine) ora combination of hardware and software. For example, any moduledescribed of the AR system 124 may physically include an arrangement ofone or more of the processors 610 (e.g., a subset of or among the one ormore processors of the machine) configured to perform the operationsdescribed herein for that module. As another example, any module of theAR system 124 may include software, hardware, or both, that configure anarrangement of one or more processors 610 (e.g., among the one or moreprocessors of the machine) to perform the operations described hereinfor that module. Accordingly, different modules of the AR system 124 mayinclude and configure different arrangements of such processors 610 or asingle arrangement of such processors 610 at different points in time.Moreover, any two or more modules of the AR system 124 may be combinedinto a single module, and the functions described herein for a singlemodule may be subdivided among multiple modules. Furthermore, accordingto various example embodiments, modules described herein as beingimplemented within a single machine, database, or device may bedistributed across multiple machines, databases, or devices.

FIG. 7A includes a depictions of an exemplary AR interface 700 todisplay an AR presentation of media content, according to certainexample embodiments. As seen in FIG. 7, the AR interface 700 includes apresentation 706A of a space, a graphical element 702A, and anindication 704A of a location of a client device 102, wherein the clientdevice 102 is a source of the graphical element 702A.

The AR interface 700 depicted in FIG. 7 may be generated based on themethods 800, 900, and 1000 of FIGS. 8, 9, and 10 respectively. As shownin FIG. 7, the AR interface 700 comprises a presentation 706A of aspace, that includes a graphical element 702A presented at a pointwithin the presentation 706A, and an indication 704A of the location ofthe client device (e.g., client device 102) which caused display of thegraphical element 702A.

For example, the AR system 124 may receive user inputs from a firstclient device to render the graphical element 702A at the point withinthe space depicted by the presentation 706A, wherein the first clientdevice is at a first location. The user inputs may include rotation andtranslation inputs to adjust and alter an orientation of the graphicalelement 702A within the presentation of the space 706A. A second clientdevice may cause display of the presentation 706A. From the perspectiveof the second client device, the graphical element 702A appears to befloating above the location of the first client device. The indication704A may therefore provide an indication of the location of the firstclient device.

In some example embodiments, a user of the second client device mayprovide one or more user inputs interacting with the graphical element702A, into the AR interface 700. For example, the user inputs mayinclude tactile inputs, such as tapping, flicking, swiping, pinching, orspreading the graphical element 702A in the presentation 706A. Inresponse to receiving such inputs, the AR system 124 may re-render thegraphical element 702A at the first client device and the second clientdevice, in real time. Thus, a user of the first client device may bepresented with changes and adjustments to the size, position, as well aslocation of the graphical element 702A at a presentation displayed atthe first client device.

In some example embodiments, the graphical element 702A may includecoded data, such as a matrix barcode. For example, an image depicted bythe graphical element 702A may be embedded with a matrix barcode such asa QR code. In response to displaying the presentation 706A that includesthe graphical element 702A which includes the coded data, a clientdevice 102 may cause the AR system 124 to retrieve and cause display ofmedia content associated with the coded data. For example, the codeddata may be associated with a media item within a database incommunication with the AR system 124. The AR system 124 may receive anindication that a client device 102 has displayed the graphical element702A that includes coded data. In response, the AR system 124 mayretrieve the associated media item and cause display of the associatedmedia item at the client device 102.

In some example embodiments, the graphical element 702A may include anephemeral element, wherein the ephemeral element has an associateddisplay duration. The AR system 124 may detect an expiration of thedisplay duration, and in response, remove the graphical element 702Afrom the presentation 706A.

FIG. 7B is a diagram illustrating the AR interface 700 generated by theAR system 124, according to certain example embodiments. As seen in FIG.7, the AR interface 700 includes a presentation 706B of a space, agraphical element 702B, an indication 704B of a location of a clientdevice 102, wherein the client device 102 is a source of the graphicalelement 702A, and an obstruction 708B, wherein the obstruction 708Bobstructs a perspective of the graphical element 702B.

In some example embodiments, in response to detecting the obstruction708B within the presentation 706B of the space, the AR system 124 mayalter the graphical element 702B such that only a portion of thegraphical element 702B is rendered within the presentation 706B. The ARsystem 124 may employ a number of image recognition and edge detectiontechniques to detect the obstruction 708B within the presentation 706B.The AR system 124 may then alter the graphical element 702B based onproperties of the obstruction 708B. In some example embodiments, the ARsystem 124 determines a distance between a viewing user (e.g., a userdisplaying the AR interface 700 at a client device) and the obstruction708B, and may render the graphical element 702B within the presentationof the space 706B based on the distance and the obstruction 708B.

For example, in some embodiments, the AR system 124 may detect theobstruction 708B through image segmentation techniques. For example,before rendering the graphical element 702B within the presentation ofthe space 706B, the AR system 124 may segment the presentation of thespace 706B into foreground and background portions, or by identifying asky depicted in the image. The AR system 124 may then determine arelative position of the graphical element 702B, based on the locationspecified by the user, to determine whether the graphical element 702Bis to be rendered in the foreground or in the background. The AR system124 may thus identify elements within the presentation of the space 706Bthat are obstructions, such as the obstruction 708B.

FIG. 8 is a flowchart illustrating various operations of the AR system124 in performing a method 800 for causing display of an augmentedreality presentation of a space, according to certain exampleembodiments. Operations of the method 800 may be performed by themodules described above with respect to FIG. 6. As shown in FIG. 8, themethod 800 includes one or more operations 802, 804, 806, and 808.

At operation 802, the display module 602 causes display of a firstpresentation of a space at a first client device (e.g., client device102). For example, the client device 102 may include a digital camera,or receive image from a digital camera, and display a presentation at adisplay of the client device 102 based on image data received from thedigital camera. In some example embodiments, the first presentation ofthe space may be displayed within a graphical user interface displayedat the first client device.

At operation 804, the AR module 604 receives a selection of a pointwithin the first presentation of the space. For example, a user of thefirst client device may provide a user input specifying the point. Theuser input may include a tactile input into a touch enabled device. Thelocation module 608 may retrieve location data that includes geolocationcoordinates associated with the selected point, as well as an altitudeor an estimate of the altitude, of the selected point.

In some example embodiments, in response to receiving the user inputselecting the point within the first presentation of the space at thefirst client device, the AR module 604 may cause display of an augmentedreality configuration interface within the graphical user interface atthe first client device. The augmented reality configuration interfacemay for example include a presentation of a set of graphical elements,as well as interfaces to receive user inputs defining properties of thegraphical elements. For example, the properties may include a size,color, style, display duration (for the ephemeral timer system 202), aswell as a list of users which the graphical element may be visible to inan AR display. The user may provide one or more inputs selecting one ormore graphical elements, and defining properties of the graphicalelement to be displayed. In some example embodiments, the user maysimply draw the graphical element directly into the first presentationof the space via a drawing tool (e.g., a digital pen). For example, theuser may provide a tactile input tracing a graphical element directlyinto the first presentation of the space. At operation 806, the ARmodule 604 renders the selected (or drawn) graphical element at thepoint within the first presentation of the space at the first clientdevice. The user may additionally provide inputs adjusting anorientation of the graphical element. For example, the user may rotateor translate the graphical element within the presentation of the space.

In some example embodiments, the AR module 604 assigns the location dataof the selected point to the graphical element selected by the user,such that the graphical element is “tied” to the location. In this way,as a client device 102 displays the space that includes the point, theAR module 604 determines that the point is within a presentation of thespace at the client device 102, and in response may retrieve thegraphical element to be displayed within the presentation of the spaceat the client device 102.

At operation 808, the display module 602 receives a request to display asecond presentation of the space from a second client device (e.g., asecond client device 102 from among the client devices 102). In responseto receiving the request to display the second presentation of the spaceat the second client device, the display module 602 generates and causesdisplay of the second presentation of the space at the second clientdevice, wherein the second presentation of the space includes thegraphical element at the point within the second presentation.

FIG. 9 is a flowchart illustrating various operations of the AR system124 in performing a method 900 for causing display of an augmentedreality presentation of a space, according to certain exampleembodiments. Operations of the method 900 may be performed by themodules described above with respect to FIG. 6. As shown in FIG. 9, themethod 900 includes one or more operations 902, 904, and 906. The method900 may be performed as part (e.g., a precursor task, a subroutine, or aportion) of the method 800, according to some example embodiments.

Operation 902 may be performed as a precursor task to operation 804 ofthe method 800, as depicted in FIG. 8. At operation 902, the locationmodule 608 determines a location of the first client device in responseto a user of the first client device providing a user input that selectsa point within the first presentation of the space. The location of thefirst client device may include geolocation coordinate as well as analtitude of the first client device. In response to receiving the userinput, the display module 602 may cause the personalization module 606to retrieve location data from the client device 102 (e.g., the firstclient device), wherein the location data indicates a location and analtitude of the first client device. For example, location module 608may utilize a Global Positioning System (GPS) to determine a locationand altitude of the first client device.

At operation 904, the AR module 604 determines a perspective of thefirst client device relative to the point selected by the user of thefirst client device, based on the location data. The perspective of thefirst client device may be defined as a field of view from the locationof the first client device, wherein the field of view is the extent ofthe space that is observable by the user through the first clientdevice. The perspective may also include an angular extent, wherein theangular extent defines a viewing angle of the first client device withrespect to the selected point within the space.

At operation 906, the AR module 604 renders the graphical element at thepoint within the first presentation of the space at the first clientdevice, based on the perspective of the first client device relative tothe selected point. In some example embodiments, the AR module 604 maydetermine an orientation of the graphical element based on theperspective of the first client device relative to the selected point.In some embodiments, the user may provide inputs adjusting theorientation of the graphical element by rotating or translating thegraphical element via various user inputs. Based on the orientation ofthe graphical element, the AR module 604 may alter a rendering of thegraphical element by adjusting properties of the graphical element suchas height, width, or color. The AR module 604 may make adjustments tothe rendering of the graphical element in real time, as location data isretrieved from the first client device, and the perspective of the firstclient device is calculated and recalculated.

FIG. 10 is a flowchart illustrating various operations of the AR system124 in performing a method 1000 for causing display of an augmentedreality presentation of a space, according to certain exampleembodiments. Operations of the method 1000 may be performed by themodules described above with respect to FIG. 6. As shown in FIG. 10, themethod 1000 includes one or more operations 1002, 1004, and 1006. Themethod 1000 may be performed as part (e.g., a precursor task, asubroutine, or a portion) of the method 800, according to some exampleembodiments.

Operation 1002 may be performed in response to operation 804, whereinthe AR module 604 receives a selection of a point within the firstpresentation of the space. In response to receiving the selection of thepoint, the location module 608 retrieves location data associated withthe first client device (e.g., a client device 102).

Operations 1004 and 1006 may be performed as a subroutine of operation808 of the method 800, as depicted in FIG. 8. At operation 808, thedisplay module 602 receives a request to display the second presentationof the space from a second client device. In response to receiving therequest to display the second presentation of the space at the secondclient device, the location module 608 identifies the location of thefirst client device within the second presentation of the space, basedon the location data from the first client device.

At operation 1006, the AR module 604 renders the graphical elementwithin the second presentation of the space at the second client device,wherein the graphical element includes an indication of the location ofthe first client device. For example, the indication of the location ofthe first client device may include a line segment or similar featureleading from the graphical element to the location of the first clientdevice within the second presentation of the space.

Software Architecture

FIG. 11 is a block diagram illustrating an example software architecture1106, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 11 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1106 may execute on hardwaresuch as machine 700 of FIG. 11 that includes, among other things,processors 1104, memory 1114, and I/O components 1118. A representativehardware layer 1152 is illustrated and can represent, for example, themachine 1100 of FIG. 11. The representative hardware layer 1152 includesa processing unit 1154 having associated executable instructions 1104.Executable instructions 1104 represent the executable instructions ofthe software architecture 1106, including implementation of the methods,components and so forth described herein. The hardware layer 1152 alsoincludes memory and/or storage modules memory/storage 1156, which alsohave executable instructions 1104. The hardware layer 1152 may alsocomprise other hardware 1158.

In the example architecture of FIG. 11, the software architecture 1106may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1106may include layers such as an operating system 1102, libraries 1120,applications 1116 and a presentation layer 1114. Operationally, theapplications 1116 and/or other components within the layers may invokeapplication programming interface (API) API calls 1108 through thesoftware stack and receive a response as in response to the API calls1108. The layers illustrated are representative in nature and not allsoftware architectures have all layers. For example, some mobile orspecial purpose operating systems may not provide aframeworks/middleware 1118, while others may provide such a layer. Othersoftware architectures may include additional or different layers.

The operating system 1102 may manage hardware resources and providecommon services. The operating system 1102 may include, for example, akernel 1122, services 1124 and drivers 1126. The kernel 1122 may act asan abstraction layer between the hardware and the other software layers.For example, the kernel 1122 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1124 may provideother common services for the other software layers. The drivers 1126are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1126 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1120 provide a common infrastructure that is used by theapplications 1116 and/or other components and/or layers. The libraries1120 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 1102 functionality (e.g., kernel 1122,services 1124 and/or drivers 1126). The libraries 1120 may includesystem libraries 1144 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1120 may include API libraries 1146 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphicslibraries (e.g., an OpenGL framework that may be used to render 2D and3D in a graphic content on a display), database libraries (e.g., SQLitethat may provide various relational database functions), web libraries(e.g., WebKit that may provide web browsing functionality), and thelike. The libraries 1120 may also include a wide variety of otherlibraries 1148 to provide many other APIs to the applications 1116 andother software components/modules.

The frameworks/middleware 1118 (also sometimes referred to asmiddleware) provide a higher-level common infrastructure that may beused by the applications 1116 and/or other software components/modules.For example, the frameworks/middleware 1118 may provide various graphicuser interface (GUI) functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware1118 may provide a broad spectrum of other APIs that may be utilized bythe applications 1116 and/or other software components/modules, some ofwhich may be specific to a particular operating system 1102 or platform.

The applications 1116 include built-in applications 1138 and/orthird-party applications 1140. Examples of representative built-inapplications 1138 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 1140 may include anapplication developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1140 may invoke the API calls 1108 provided bythe mobile operating system (such as operating system 1102) tofacilitate functionality described herein.

The applications 1116 may use built in operating system functions (e.g.,kernel 1122, services 1124 and/or drivers 1126), libraries 1120, andframeworks/middleware 1118 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 1114. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 12 is a block diagram illustrating components of a machine 1200,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 12 shows a diagrammatic representation of the machine1200 in the example form of a computer system, within which instructions1210 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 1200 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 1210 may be used to implement modules or componentsdescribed herein. The instructions 1210 transform the general,non-programmed machine 1200 into a particular machine 1200 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 1200 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 1200 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 1200 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 1210, sequentially or otherwise, that specify actions to betaken by machine 1200. Further, while only a single machine 1200 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 1210 to perform any one or more of the methodologiesdiscussed herein.

The machine 1200 may include processors 1204, memory memory/storage1206, and I/O components 1218, which may be configured to communicatewith each other such as via a bus 1202. The memory/storage 1206 mayinclude a memory 1214, such as a main memory, or other memory storage,and a storage unit 1216, both accessible to the processors 1204 such asvia the bus 1202. The storage unit 1216 and memory 1214 store theinstructions 1210 embodying any one or more of the methodologies orfunctions described herein. The instructions 1210 may also reside,completely or partially, within the memory 1214, within the storage unit1216, within at least one of the processors 1204 (e.g., within theprocessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 1200. Accordingly, the memory 1214, thestorage unit 1216, and the memory of processors 1204 are examples ofmachine-readable media.

The I/O components 1218 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 1218 that are included in a particular machine 1200 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 1218 may include many other components that are not shown inFIG. 12. The I/O components 1218 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the I/O components 1218may include output components 1226 and input components 1228. The outputcomponents 1226 may include visual components (e.g., a display such as aplasma display panel (PDP), a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 1228 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 1218 may includebiometric components 1230, motion components 1234, environmentalenvironment components 1236, or position components 1238 among a widearray of other components. For example, the biometric components 1230may include components to detect expressions (e.g., hand expressions,facial expressions, vocal expressions, body gestures, or eye tracking),measure biosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 1234 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environment components 1236 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment. The position components 1238 mayinclude location sensor components (e.g., a Global Position system (GPS)receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 1218 may include communication components 1240operable to couple the machine 1200 to a network 1232 or devices 1220via coupling 1222 and coupling 1224 respectively. For example, thecommunication components 1240 may include a network interface componentor other suitable device to interface with the network 1232. In furtherexamples, communication components 1240 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 1220 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, the communication components 1240 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 1240 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components1240, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

Glossary

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible medium to facilitate communication of suchinstructions. Instructions may be transmitted or received over thenetwork using a transmission medium via a network interface device andusing any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smart phones, tablets, ultra books, netbooks,laptops, multi-processor systems, microprocessor-based or programmableconsumer electronics, game consoles, set-top boxes, or any othercommunication device that a user may use to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), the Internet, a portion of theInternet, a portion of the Public Switched Telephone Network (PSTN), aplain old telephone service (POTS) network, a cellular telephonenetwork, a wireless network, a Wi-Fi® network, another type of network,or a combination of two or more such networks. For example, a network ora portion of a network may include a wireless or cellular network andthe coupling may be a Code Division Multiple Access (CDMA) connection, aGlobal System for Mobile communications (GSM) connection, or other typeof cellular or wireless coupling. In this example, the coupling mayimplement any of a variety of types of data transfer technology, such asSingle Carrier Radio Transmission Technology (1×RTT), Evolution-DataOptimized (EVDO) technology, General Packet Radio Service (GPRS)technology, Enhanced Data rates for GSM Evolution (EDGE) technology,third Generation Partnership Project (3GPP) including 3G, fourthgeneration wireless (4G) networks, Universal Mobile TelecommunicationsSystem (UMTS), High Speed Packet Access (HSPA), WorldwideInteroperability for Microwave Access (WiMAX), Long Term Evolution (LTE)standard, others defined by various standard setting organizations,other long range protocols, or other data transfer technology.

“EPHEMERAL MESSAGE” in this context refers to a message that isaccessible for a time-limited duration. An ephemeral message may be atext, an image, a video and the like. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, deviceor other tangible media able to store instructions and data temporarilyor permanently and may include, but is not be limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity or logichaving boundaries defined by function or subroutine calls, branchpoints, application program interfaces (APIs), or other technologiesthat provide for the partitioning or modularization of particularprocessing or control functions. Components may be combined via theirinterfaces with other components to carry out a machine process. Acomponent may be a packaged functional hardware unit designed for usewith other components and a part of a program that usually performs aparticular function of related functions. Components may constituteeither software components (e.g., code embodied on a machine-readablemedium) or hardware components. A “hardware component” is a tangibleunit capable of performing certain operations and may be configured orarranged in a certain physical manner. In various example embodiments,one or more computer systems (e.g., a standalone computer system, aclient computer system, or a server computer system) or one or morehardware components of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a Field-Programmable Gate Array (FPGA) or an ApplicationSpecific Integrated Circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In embodiments in which multiple hardwarecomponents are configured or instantiated at different times,communications between such hardware components may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware components have access. Forexample, one hardware component may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware component may then, at alater time, access the memory device to retrieve and process the storedoutput. Hardware components may also initiate communications with inputor output devices, and can operate on a resource (e.g., a collection ofinformation). The various operations of example methods described hereinmay be performed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an Application ProgramInterface (API)). The performance of certain of the operations may bedistributed among the processors, not only residing within a singlemachine, but deployed across a number of machines. In some exampleembodiments, the processors or processor-implemented components may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the processors or processor-implemented components may bedistributed across a number of geographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands”, “op codes”, “machine code”, etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an Application SpecificIntegrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC)or any combination thereof. A processor may further be a multi-coreprocessor having two or more independent processors (sometimes referredto as “cores”) that may execute instructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, forexample giving date and time of day, sometimes accurate to a smallfraction of a second.

“LIFT” in this context is a measure of the performance of a targetedmodel at predicting or classifying cases as having an enhanced response(with respect to a population as a whole), measured against a randomchoice targeting model.

What is claimed is:
 1. A system comprising: a memory; and at least onehardware processor coupled to the memory and comprising instructionsthat causes the system to perform operations comprising: receiving arequest that includes an identification of a location from a firstclient device; identifying a second client device at the locationidentified by the request from the first client device in response tothe request that includes the identification of the location; accessinglocation data from the second client device in response to theidentification of the second client device at the location; generating agraphical element that comprises an indicator based on a set of userinputs that define properties of the graphical element, the indicatorcomprising a display duration that defines a period of time to displaythe graphical element; and causing display of a presentation of imagedata at the first client device, the presentation of the image dataincluding a display of the indicator at a position within thepresentation of the image data, the indicator comprising a projectionthat extends from a location that corresponds with the second clientdevice within the image data based on the location data from the secondclient device and the display duration.
 2. The system of claim 1,wherein the operations further comprise: accessing a user profileassociated with a user of the second client device, the user profileincluding a set of user preferences; and generating the indicator basedon the set of user preferences.
 3. The system of claim 1, wherein thecausing display of the presentation of the image data at the firstclient device further comprises: determining a perspective of the firstclient device relative to the location of the second client device; andcausing display of the presentation of the image data at the firstclient device based on the perspective of the first client device. 4.The system of claim 3, wherein the detecting the perspective of thefirst client device relative to the location of the second client devicefurther comprises: detecting an obstruction based on the perspective ofthe first client device, the obstruction comprising properties; andwherein the causing display of the presentation of the image data at thefirst client device based on the perspective of the first client deviceincludes: rendering a portion of the image data based on the propertiesof the obstruction.
 5. The system of claim 1, wherein the operationsfurther comprise: detecting an expiration of the display duration of theindicator; and removing the indicator from the presentation of the imagedata at the first client device based on the expiration of the displayduration.
 6. The system of claim 1, wherein the indicator comprisescoded data, and the operations further comprise: detecting the codeddata at the first client device based on the causing display of thepresentation of the image data that includes the display of theindicator; retrieving media content based on the coded data in responseto detecting the coded data; and presenting the media content at thefirst client device.
 7. The system of claim 1, wherein the operationsfurther comprise: detecting an interaction with the indicator at thefirst client device; and altering the indicator based on theinteraction.
 8. A method comprising: receiving a request that includesan identification of a location from a first client device; identifyinga second client device at the location identified by the request fromthe first client device in response to the request that includes theidentification of the location; accessing location data from the secondclient device in response to the identification of the second clientdevice at the location; generating a graphical element that comprises anindicator based on a set of user inputs that define properties of thegraphical element, the indicator comprising a display duration thatdefines a period of time to display the graphical element; and causingdisplay of a presentation of image data at the first client device, thepresentation of the image data including a display of the indicator at aposition within the presentation of the image data, the indicatorcomprising a projection that extends from a location that correspondswith the second client device within the image data based on thelocation data from the second client device and the display duration. 9.The method of claim 8, wherein the method further comprises: accessing auser profile associated with a user of the second client device, theuser profile including a set of user preferences; and generating theindicator based on the set of user preferences.
 10. The method of claim8, wherein the causing display of the presentation of the image data atthe first client device further comprises: determining a perspective ofthe first client device relative to the location of the second clientdevice; and causing display of the presentation of the image data at thefirst client device based on the perspective of the first client device.11. The method of claim 10, wherein the detecting the perspective of thefirst client device relative to the location of the second client devicefurther comprises: detecting an obstruction based on the perspective ofthe first client device, the obstruction comprising properties; andwherein the causing display of the presentation of the image data at thefirst client device based on the perspective of the first client deviceincludes: rendering a portion of the image data based on the propertiesof the obstruction.
 12. The method of claim 8, wherein the methodfurther comprises: detecting an expiration of the display duration; andremoving the indicator from the presentation of the image data at thefirst client device based on the expiration of the display duration. 13.The method of claim 8, wherein the indicator comprises coded data, andthe method further comprises: detecting the coded data at the firstclient device based on the causing display of the presentation of theimage data that includes the display of the indicator; retrieving mediacontent based on the coded data in response to detecting the coded data;and presenting the media content at the first client device.
 14. Themethod of claim 8, wherein the method further comprises: detecting aninteraction with the indicator at the first client device; and alteringthe indicator based on the interaction.
 15. A non-transitorymachine-readable storage medium comprising instructions that, whenexecuted by one or more processors of a machine, cause the machine toperform operations comprising: receiving a request that includes anidentification of a location from a first client device; identifying asecond client device at the location identified by the request from thefirst client device in response to the request that includes theidentification of the location; accessing location data from the secondclient device in response to the identification of the second clientdevice at the location; generating a graphical element that comprises anindicator based on a set of user inputs that define properties of thegraphical element, the indicator comprising a display duration thatdefines a period of time to display the graphical element; and causingdisplay of a presentation of image data at the first client device, thepresentation of the image data including a display of the indicator at aposition within the presentation of the image data, the indicatorcomprising a projection that extends from a location that correspondswith the second client device within the image data based on thelocation data from the second client device and the display duration.16. The non-transitory machine-readable storage medium of claim 15,wherein the operations further comprise: accessing a user profileassociated with a user of the second client device, the user profileincluding a set of user preferences; and generating the indicator basedon the set of user preferences.
 17. The non-transitory machine-readablestorage medium of claim 15, wherein the causing display of thepresentation of the image data at the first client device furthercomprises: determining a perspective of the first client device relativeto the location of the second client device; and causing display of thepresentation of the image data at the first client device based on theperspective of the first client device.
 18. The non-transitorymachine-readable storage medium of claim 17, wherein the detecting theperspective of the first client device relative to the location of thesecond client device further comprises: detecting an obstruction basedon the perspective of the first client device, the obstructioncomprising properties; and wherein the causing display of thepresentation of the image data at the first client device based on theperspective of the first client device includes: rendering a portion ofthe image data based on the properties of the obstruction.
 19. Thenon-transitory machine-readable storage medium of claim 15, wherein theoperations further comprise: detecting an expiration of the displayduration; and removing the indicator from the presentation of the imagedata at the first client device based on the expiration of the displayduration.
 20. The non-transitory machine-readable storage medium ofclaim 15, wherein the indicator comprises coded data, and the operationsfurther comprise: detecting the coded data at the first client devicebased on the causing display of the presentation of the image data thatincludes the display of the indicator; retrieving media content based onthe coded data in response to detecting the coded data; and presentingthe media content at the first client device.